home *** CD-ROM | disk | FTP | other *** search
-
-
- !!!!! *YOU* *MUST* read the last paragraph about problems !!!!!
-
- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- !!!!! Don`t wonder about the new size of the Updates and that !!!!!
- !!!!! Updater doesn`t print all module versions anymore. !!!!!
- !!!!! This is NO bug. The modules are still there. !!!!!
- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
- New Upgrade features:
-
- o WideTermination check
- A lot people don`t seem to have read the manual correctly
- and use Wide/Narrow bridges without upper Widebus termination
- which leads to not working reselection.
- (Syndrom: 44.2 works perfectly with your devices but only slowly)
- If the check detects such broken SCSI configuration the device
- completely disables reselection for all units.
- (CDROM is reselection by default)
-
- ATTENTION:
- Correct Termination checks are NOT 100%.
-
-
- o New Unit ID standard so it works with WIDE HDs.
- Board * 10*1000*1000
- Lun * 10*1000
- Unit * 10
- + 8 (8 in the last digit switches the format)
-
- so if you wanna access Unit 13 Lun 5 it would look like
-
- 500138
-
- or Unit 8 Lun 0
-
- 88
-
- or Unit 1 Lun 0
-
- 18 (NewStyle)
-
- or
-
- 1 (OldStyle)
-
- The old Format was
-
- Board * 100
- Lun * 10
- Unit * 1
-
- so everybody sees that you could only use 9 Units and Wide
- provides 15. I know the the use of Unit=8 as a flag isn`t
- elegant but it`s the only compatible system i found.
-
- o Key "2" disables the processor on an 1200 ONLY.
- o Key "s" pressed during booting disables the SCSI
- also disables the bootmenu, bootmenu settings,
- 31khz monitor and so on.
- o Key "m" pressed during booting disables the memory
- o Key "a" pressed during booting disables all
-
- o BootMenu which can be invoked by holding
- the Key <ESC> key during the system boot.
- (Only works on systems with SCSI)
-
- The Bootmenu now ALWAYS pops up in 31khz mode, so
- folks with an A2024 parallel to their normal monitor
- will have bad luck. But I assume that a generell 31Khz
- Boot monitor is more useful than this problem for users
- with that setup.
-
-
- Then you see a menu with the 3 entries
-
- o SCSI
- o List with 8 or 16(WideSCSI) Units.
- The entries show the current settings for the UnitID.
- The Controller UnitID entry is marked differently.
- If you click on the UnitID you get into a simular menu
- like Unitcontrol`s Option menu.
- If you click on the controller UnitID entry you get into
- a simular menu like Unitcontrol`s Prefs menu.
-
- Unit prefs:
-
- o NO LUN
- 1 LUN
- 2 LUNs
- 3 LUNs
- 4 LUNs
- 5 LUNs
- 6 LUNs
- 7 LUNs
- 8 LUNs
-
- -> This Entry can be used to disable the scan for the whole
- unit for more Luns which can speed up booting a lot.
-
- o Offset
- Here you specify the synchron handshake.
-
- o Period
- Here you specify the synchron clock.
-
- o ASynchron/Synchron
- ASynchron
- Synchron
-
- Here you enable the synchron mode, so you
- can change Offset and Period now.
- The ASynchron/Synchron mode means that the
- synchron mode is activated if specified by
- the RDB for example.(The AUTO mode)
-
- o Auto Buswidth
- 8-Bit
- 16-Bit
-
- Here you specify the buswidth for a unit.
- Well..anything more than Auto Mode isn`t really
- needed.
-
- o Auto Reselection
- No Reselection
- Reselection
-
- Disabling reselection for units with problems is
- possible here. Auto Mode means that reselection
- is activated if the RDB flag is set or if it has
- no RDB but is a normal unit like a cdrom.
- Scanners and other esotheric units don`t use
- reselection in AUTO mode.
-
-
- o CDBoot Pri
- define the cdrom boot priority. Check the System Bootmenu for
- the boot priority of other devices.
-
-
- o CDRom Device Name
- define the device name with which the cdrom should be mounted.
-
- o No CDRom Bount
- CDRom Mount
- CDRom Boot
-
- The buildin CDRom filesystem is the old Phase5 CDRive filesystem.
- Its feature set may not be enough for your needs.
-
-
- Controller Prefs:
-
- o BusID
- Controller BusID..normally 7.
- The BusID of the controller. This doesn`t mean you
- can use SCSI Nets as these don`t work in general.
-
- o SCSIResetDelay
- The seconds the device waits after the first
- SCSI Reset/Init.
-
- o ErrorDelay
- The seconds the device waits after an Inquiry Error
-
- o RemovableDelay
- The second intervall for a removable check
-
- o ErrorDelayRetry
- The retry count for an Inquiry after an Error.
-
- o ErrorRetry
- The retry count for an SCSI Operation after an SCSI Error.
-
- o TimeOut
- (not yet used)
-
-
- o CDFS
-
- o No CDFS HD RDB Scan
- CDFS HD RDB Scan
-
- Update the filesystem.resource with CDFS filesystems when these
- are placed in the RDB of HDs **BEFORE** the CD Drive at the same
- controller. This way you can theoretically use other cdfilesystems.
- *Theoretically* means that i haven`t tested if other cd filesystem
- work with such startup as they may need to find their prefs.
-
- The CDFS dostype is
-
- #define ID_CDFS_DISK (0x43444653L) /* 'CDFS' */
- The new SCSIConfig has an automatic filesystem entry for this.
-
- o Cache Sets
- How many Cache Sets are allocated.
- CacheSets*CacheSetBlocks*2048 is the memory needed.
- Only useful for CDFS
-
- o Cache Set Blocks
- The number of of each cache set.
- A cache set is the line of block at Sector & ~(CacheSetBlocks-1) which
- is fetched into the cache.
- Only useful for CDFS
-
- o RAM
-
- o MemorySpeed 70ns
- -> standard waitstates
- MemorySpeed 60ns
- -> for 50Mhz 060 / 66Mhz PowerPC cards this means
- o 68k No Read Waitstate
- o 68k No Write Waitstate
- o PPC No Read Waitstate
- o PPC No Write Waitstate
-
- Free Config
-
- o 68k Read Waitstate
- 68k No Read Waitstate
- -> possible with at least 70ns rams
-
- o 68k Write Waitstate
- 68k No Write Waitstate
- -> possible with at least 70ns rams
-
- o 68k PreCharge
- 68k No PreCharge
- possible with at least 60ns rams but not guranteed
- to work with every ram.
- (Enabled only for boards supporting this)
-
- o PPC Read Waitstate
- PPC No Read Waitstate
- possible with at least 60ns rams
-
- o PPC Write Waitstate
- PPC No Write Waitstate
- possible with at least 60ns rams
-
- o PPC PreCharge
- PPC No PreCharge
- possible with at least 60ns rams but not guranteed
- to work with every ram.
- (Enabled only for boards supporting this)
-
- o SYSTEM
-
- o No MapRom
- MapRom
- -> *current* kickstart ROM is mapped
-
- o No MacPatch
- MacPatch
- -> the mapped kickstart`s chipram starts at 0x4000
- to avoid shapeshifter/fusion hack tools.
- Only tested with 40.68
-
- o No SCSIPatch
- SCSIPatch
- -> the mapped kickstart`s scsi.device is disabled.
- This means for the A4000 that IDE is off
- and for A3000 that the on board SCSI is off.
-
- o No NCR SCSIPatch
- NCR SCSIPatch
- -> the mapped kickstart`s NCR scsi.device is disabled.
- This only works on the A4000T and means that
- the on board SCSI is off.
-
- o No 31Khz Screen
- 31Khz Default Screen
- ->Uses the 31khz 640*400 BootMonitor now also for the
- AmigaOS BootMenu and for the initial shell.
- When IPrefs is started the 31Khz Bootmonitor patch
- get inactive.
-
- *ATTENTION*
-
- I set the hardware into best mode, which means
- that it boots into AGA mode, if a Boot31Khz Screen
- is opened. Normally BestMode is set with setpatch,
- so setting it before may have consequences for old
- games.
-
- o SuperScalar No
- SuperScalar Yes
- ->Enables superscalar mode to speed up booting.
- This mode is activated with the 68060.library later
- anyway.
-
- o BranchCache No
- BranchCache Yes
- ->Enables the branchcache to speed up booting.
- This mode is activated with the 68060.library later
- anyway.
-
- o WriteBuffer No
- WriteBuffer Yes
- ->Enables the writebuffer to speed up booting.
- This mode is activated with the 68060.library later
- anyway.
-
- o SAVE | USE | CANCEL
-
- - SAVE saves the settings into the flashrom which
- means that these settings are used for every coldboot
- or warmboot if not changed or *NEW FLASH UPDATE* is
- done. With the help of the 2nd joystickport`s button
- you can completely disable scsi device and settings
- if you have for some reason a problem to get into the
- new bootmenu after playing around with special settings.
- So you SHOULD HAVE the PPCUpdate/MK3Update on a disk so
- you can quickly reinstall it without a hd which is
- connected to the CyberStorm.
-
- - USE uses the current changed settings for the current boot.
- The settings aren`t saved and are lost in the next reset.
-
- - CANCEL doesn`t use the settings.
-
-
- How to solve Problems ?
-
- o If you have weird crashes you probably have a power problem.
- Even if you have a bigger power supply the problem can be
- occur because the small power connection to the A1200 board
- by certain towers can`t transport the needed power so the
- ppc board gets unstable. To work around this problem
- you should create a 2nd connection from the A1200 to the
- power supply. Several people used the floppy connectors.
-
- o If you have problems with 60ns mode your simms need significant
- more power in 60ns mode which is a problem.
- Read the first section how to fix about power problems.
- Besides this...60ns printed on a Simm don`t necessary mean
- that it`s a real 60ns Simm.
-
- o If you`re using at least 1 Ultra unit on the bus be *very*
- careful with the length of the cable.
-
- o If you use a 68/50 adapter and use more than one unit on
- this new chain or let the wide chain end here with one unit
- this adapter MUST BE active terminated on the wide lines.
-
- o At least one unit must provide TERM power.
-
- o The controller is NOT terminated
-
- o If you have problems and can`t boot with a certain setup
- try to disable units in the Bootmenu until you`re able to
- boot. Then use Unitcontrol Rescan and you may get device
- error requesters.
- If you get parity errors for example you have a serious
- cable/term problem.
- The device has absolutely nothing to do with that.
-
- o IBM and (Seagate ?..not mine) drives have problems with
- the device when the SDTR Jumpers are set.
- I can`t see what is exactly happening then because i
- don`t have such drive.
-
- **************************************************************************
- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- --------------------------------------------------------------------------
- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- **************************************************************************
- o You use AmiCDFS or other CDFilesystems and the new BlizzardPPC or
- CyberstormPPC FlashUpdate is installed.
- It does NOT matter if you have a SCSI or not...it also effects IDE.
-
- Change the 0x43444653 (CDFS) dostype in the (AmiCDFS) mountlist.
- Add a 1 at the last number for example.
- OR
- add the line FORCELOAD = 1
-
- otherwise it`s using the Phase5 CDFilesystem which may
- not do what you want it to do.
- The CDRive filesystem is always added to the filesystem.resource
- with the 0x43444653 ID
-
- **************************************************************************
- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- --------------------------------------------------------------------------
- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- **************************************************************************
-
- o SYSIHack Problem...SYSIHack says that iprefs was already
- started which it wasn`t. (Caused by opening gadtools.library
- in the rom)
-
- Enter the BootMenu GUI, then leave it...SysIHack won`t
- start because it checks if the gadtools.library is already
- used. The gadtools.library can`t be expunged so there`s
- no cure for this problem.
-
- o Only use the real Setpatch 40.16. The last CBM had released.
-
- o Don`t use skick as people reported problems with it.
- Use cybermap instead.
-